Skip to content

build(deps): bump the rust-dependencies group across 5 directories with 5 updates - #795

Open
dependabot[bot] wants to merge 3 commits into
mainfrom
dependabot/cargo/rust-dependencies-c6a39897ed
Open

build(deps): bump the rust-dependencies group across 5 directories with 5 updates#795
dependabot[bot] wants to merge 3 commits into
mainfrom
dependabot/cargo/rust-dependencies-c6a39897ed

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 27, 2026

Copy link
Copy Markdown
Contributor

Bumps the rust-dependencies group with 4 updates in the / directory: uuid, jsonschema, yaml_serde and vstd.
Bumps the rust-dependencies group with 4 updates in the /bindings/ffi directory: uuid, jsonschema, yaml_serde and vstd.
Bumps the rust-dependencies group with 4 updates in the /bindings/java directory: uuid, jsonschema, yaml_serde and vstd.
Bumps the rust-dependencies group with 5 updates in the /bindings/python directory:

Package From To
uuid 1.24.1 1.25.0
jsonschema 0.49.9 0.51.0
yaml_serde 0.10.6 0.10.7
vstd 0.0.0-2026-08-09-0044 0.0.0-2026-08-23-0033
ordered-float 5.3.0 5.5.0

Bumps the rust-dependencies group with 4 updates in the /bindings/wasm directory: uuid, jsonschema, yaml_serde and vstd.

Updates uuid from 1.24.1 to 1.25.0

Release notes

Sourced from uuid's releases.

1.25.0

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@v1.24.1...1.25.0

Commits
  • 302e0bf Merge pull request #903 from uuid-rs/cargo/1.25.0
  • b7ccde8 prepare for 1.25.0 release
  • c62dffb Merge pull request #902 from ChrisJr404/serde-bytes-module
  • 8c198b2 Add a serde::bytes module that encodes as a byte string
  • See full diff in compare view

Updates jsonschema from 0.49.9 to 0.51.0

Release notes

Sourced from jsonschema's releases.

[Python] Release 0.51.0

Added

  • vocabularies option, declaring support for a vocabulary this library does not implement.

Fixed

  • The uniqueItems length ceiling not reading an items or contains schema written as a $ref.
  • The Draft 2020-12 Format-Assertion vocabulary read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • An unrecognized format accepted under a meta-schema requiring the Format-Assertion vocabulary (it should be rejected).
  • A meta-schema requiring a vocabulary this library does not implement accepted (it should be rejected).
  • The Draft 2019-09 Format vocabulary declared true read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • The bundled https://json-schema.org/draft/2020-12/meta/format-assertion meta-schema not declaring its vocabulary, so a schema written against it annotated format instead of asserting it.
  • A meta-schema without $id keeping its $vocabulary unread, so a schema written against it got every Draft 2020-12 vocabulary.
  • A schema naming a bundled vocabulary meta-schema as its $schema rejected as an unknown meta-schema (it should build).
  • The regex format reading the Rust regex dialect (it should read the ECMA-262 dialect in Unicode mode).
  • The uri-template format rejecting an apostrophe in a literal (it should accept it, per RFC 6570 errata 6937).
  • The duration format accepting weeks combined with a time part, such as P1WT1H (it should reject it).
  • Stack overflow compiling unevaluatedProperties or unevaluatedItems beside a $ref that cycles back to the node, written as #, through its $id, or through a chain of definitions.

Performance

  • Building unevaluatedProperties or unevaluatedItems over a deep allOf or $ref chain costs its depth instead of its square.

[Ruby] Release 0.51.0

Added

  • vocabularies option, declaring support for a vocabulary this library does not implement.

Fixed

  • The uniqueItems length ceiling not reading an items or contains schema written as a $ref.
  • The Draft 2020-12 Format-Assertion vocabulary read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • An unrecognized format accepted under a meta-schema requiring the Format-Assertion vocabulary (it should be rejected).
  • A meta-schema requiring a vocabulary this library does not implement accepted (it should be rejected).
  • The Draft 2019-09 Format vocabulary declared true read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • The bundled https://json-schema.org/draft/2020-12/meta/format-assertion meta-schema not declaring its vocabulary, so a schema written against it annotated format instead of asserting it.
  • A meta-schema without $id keeping its $vocabulary unread, so a schema written against it got every Draft 2020-12 vocabulary.
  • A schema naming a bundled vocabulary meta-schema as its $schema rejected as an unknown meta-schema (it should build).
  • The regex format reading the Rust regex dialect (it should read the ECMA-262 dialect in Unicode mode).
  • The uri-template format rejecting an apostrophe in a literal (it should accept it, per RFC 6570 errata 6937).
  • The duration format accepting weeks combined with a time part, such as P1WT1H (it should reject it).
  • Stack overflow compiling unevaluatedProperties or unevaluatedItems beside a $ref that cycles back to the node, written as #, through its $id, or through a chain of definitions.

Performance

  • Building unevaluatedProperties or unevaluatedItems over a deep allOf or $ref chain costs its depth instead of its square.

[Rust] Release 0.51.0

Added

... (truncated)

Changelog

Sourced from jsonschema's changelog.

[0.51.0] - 2026-08-23

Added

  • ValidationOptions::with_vocabulary and the vocabularies attribute on jsonschema::validator, declaring support for a vocabulary this crate does not implement.
  • The --vocabulary flag of jsonschema validate.

Changed

  • Vocabulary gained the FormatAssertion variant, which its Draft 2020-12 URI parses to instead of Vocabulary::Custom, and is marked non_exhaustive.

Fixed

  • The uniqueItems length ceiling not reading an items or contains schema written as a $ref.
  • The Draft 2020-12 Format-Assertion vocabulary read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • An unrecognized format accepted under a meta-schema requiring the Format-Assertion vocabulary (it should be rejected).
  • A meta-schema requiring a vocabulary this crate does not implement accepted (it should be rejected).
  • The Draft 2019-09 Format vocabulary declared true read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • The bundled https://json-schema.org/draft/2020-12/meta/format-assertion meta-schema not declaring its vocabulary, so a schema written against it annotated format instead of asserting it.
  • A meta-schema without $id keeping its $vocabulary unread, so a schema written against it got every Draft 2020-12 vocabulary.
  • A schema naming a bundled vocabulary meta-schema as its $schema rejected as an unknown meta-schema (it should build).
  • The regex format reading the Rust regex dialect (it should read the ECMA-262 dialect in Unicode mode).
  • The uri-template format rejecting an apostrophe in a literal (it should accept it, per RFC 6570 errata 6937).
  • The duration format accepting weeks combined with a time part, such as P1WT1H (it should reject it).
  • Stack overflow compiling unevaluatedProperties or unevaluatedItems beside a $ref that cycles back to the node, written as #, through its $id, or through a chain of definitions.

Performance

  • Building unevaluatedProperties or unevaluatedItems over a deep allOf or $ref chain costs its depth instead of its square.

[0.50.1] - 2026-08-22

Changed

  • CanonicalSchema::satisfiability answers Yes for a string whose pattern or format a matching value can be built from.
  • CanonicalSchema::satisfiability answers No where a format takes no string of the length the schema asks for.

Fixed

  • CanonicalSchema::negate taking apart a union that reads a definition through its own if, so a schema and its negation shared a value.
  • CanonicalSchema::subtract dropping a Draft 4 array member an element demand partly takes.
  • CanonicalSchema::covers answering Yes where a Draft 4 element demand refuses a member.
  • A string schema whose maxLength is 0 keeping a pattern, format, or content facet unread, so the same constraints written in one object and written as an allOf reached different canonical forms.

Performance

  • not over a wide object schema costs its branch count instead of its square.
  • not over an object schema is linear in its property count, not quadratic.
  • not over an object schema with additionalProperties: false no longer costs cubic time in its property count.

... (truncated)

Commits
  • b7fd606 chore(rust): Release 0.51.0
  • b225a20 fix: Stack overflow compiling unevaluatedProperties or unevaluatedItems b...
  • df15d19 build(deps): bump crates/jsonschema/tests/suite
  • df8b81c fix: Misc format fixes
  • 38056c7 feat: ValidationOptions::with_vocabulary and the vocabularies attribute o...
  • 31d52b2 fix: The uniqueItems length ceiling not reading an items or contains sc...
  • 5993cf1 chore(ruby): Release 0.50.1
  • e04ecc6 build(ruby): Exclude arm-linux-musl
  • 1fc21b9 chore(python): Release 0.50.1
  • 60a563d chore(rust): Release 0.50.1
  • Additional commits viewable in compare view

Updates yaml_serde from 0.10.6 to 0.10.7

Commits

Updates vstd from 0.0.0-2026-08-09-0044 to 0.0.0-2026-08-23-0033

Commits

Updates uuid from 1.24.1 to 1.25.0

Release notes

Sourced from uuid's releases.

1.25.0

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@v1.24.1...1.25.0

Commits
  • 302e0bf Merge pull request #903 from uuid-rs/cargo/1.25.0
  • b7ccde8 prepare for 1.25.0 release
  • c62dffb Merge pull request #902 from ChrisJr404/serde-bytes-module
  • 8c198b2 Add a serde::bytes module that encodes as a byte string
  • See full diff in compare view

Updates jsonschema from 0.49.9 to 0.51.0

Release notes

Sourced from jsonschema's releases.

[Python] Release 0.51.0

Added

  • vocabularies option, declaring support for a vocabulary this library does not implement.

Fixed

  • The uniqueItems length ceiling not reading an items or contains schema written as a $ref.
  • The Draft 2020-12 Format-Assertion vocabulary read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • An unrecognized format accepted under a meta-schema requiring the Format-Assertion vocabulary (it should be rejected).
  • A meta-schema requiring a vocabulary this library does not implement accepted (it should be rejected).
  • The Draft 2019-09 Format vocabulary declared true read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • The bundled https://json-schema.org/draft/2020-12/meta/format-assertion meta-schema not declaring its vocabulary, so a schema written against it annotated format instead of asserting it.
  • A meta-schema without $id keeping its $vocabulary unread, so a schema written against it got every Draft 2020-12 vocabulary.
  • A schema naming a bundled vocabulary meta-schema as its $schema rejected as an unknown meta-schema (it should build).
  • The regex format reading the Rust regex dialect (it should read the ECMA-262 dialect in Unicode mode).
  • The uri-template format rejecting an apostrophe in a literal (it should accept it, per RFC 6570 errata 6937).
  • The duration format accepting weeks combined with a time part, such as P1WT1H (it should reject it).
  • Stack overflow compiling unevaluatedProperties or unevaluatedItems beside a $ref that cycles back to the node, written as #, through its $id, or through a chain of definitions.

Performance

  • Building unevaluatedProperties or unevaluatedItems over a deep allOf or $ref chain costs its depth instead of its square.

[Ruby] Release 0.51.0

Added

  • vocabularies option, declaring support for a vocabulary this library does not implement.

Fixed

  • The uniqueItems length ceiling not reading an items or contains schema written as a $ref.
  • The Draft 2020-12 Format-Assertion vocabulary read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • An unrecognized format accepted under a meta-schema requiring the Format-Assertion vocabulary (it should be rejected).
  • A meta-schema requiring a vocabulary this library does not implement accepted (it should be rejected).
  • The Draft 2019-09 Format vocabulary declared true read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • The bundled https://json-schema.org/draft/2020-12/meta/format-assertion meta-schema not declaring its vocabulary, so a schema written against it annotated format instead of asserting it.
  • A meta-schema without $id keeping its $vocabulary unread, so a schema written against it got every Draft 2020-12 vocabulary.
  • A schema naming a bundled vocabulary meta-schema as its $schema rejected as an unknown meta-schema (it should build).
  • The regex format reading the Rust regex dialect (it should read the ECMA-262 dialect in Unicode mode).
  • The uri-template format rejecting an apostrophe in a literal (it should accept it, per RFC 6570 errata 6937).
  • The duration format accepting weeks combined with a time part, such as P1WT1H (it should reject it).
  • Stack overflow compiling unevaluatedProperties or unevaluatedItems beside a $ref that cycles back to the node, written as #, through its $id, or through a chain of definitions.

Performance

  • Building unevaluatedProperties or unevaluatedItems over a deep allOf or $ref chain costs its depth instead of its square.

[Rust] Release 0.51.0

Added

... (truncated)

Changelog

Sourced from jsonschema's changelog.

[0.51.0] - 2026-08-23

Added

  • ValidationOptions::with_vocabulary and the vocabularies attribute on jsonschema::validator, declaring support for a vocabulary this crate does not implement.
  • The --vocabulary flag of jsonschema validate.

Changed

  • Vocabulary gained the FormatAssertion variant, which its Draft 2020-12 URI parses to instead of Vocabulary::Custom, and is marked non_exhaustive.

Fixed

  • The uniqueItems length ceiling not reading an items or contains schema written as a $ref.
  • The Draft 2020-12 Format-Assertion vocabulary read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • An unrecognized format accepted under a meta-schema requiring the Format-Assertion vocabulary (it should be rejected).
  • A meta-schema requiring a vocabulary this crate does not implement accepted (it should be rejected).
  • The Draft 2019-09 Format vocabulary declared true read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • The bundled https://json-schema.org/draft/2020-12/meta/format-assertion meta-schema not declaring its vocabulary, so a schema written against it annotated format instead of asserting it.
  • A meta-schema without $id keeping its $vocabulary unread, so a schema written against it got every Draft 2020-12 vocabulary.
  • A schema naming a bundled vocabulary meta-schema as its $schema rejected as an unknown meta-schema (it should build).
  • The regex format reading the Rust regex dialect (it should read the ECMA-262 dialect in Unicode mode).
  • The uri-template format rejecting an apostrophe in a literal (it should accept it, per RFC 6570 errata 6937).
  • The duration format accepting weeks combined with a time part, such as P1WT1H (it should reject it).
  • Stack overflow compiling unevaluatedProperties or unevaluatedItems beside a $ref that cycles back to the node, written as #, through its $id, or through a chain of definitions.

Performance

  • Building unevaluatedProperties or unevaluatedItems over a deep allOf or $ref chain costs its depth instead of its square.

[0.50.1] - 2026-08-22

Changed

  • CanonicalSchema::satisfiability answers Yes for a string whose pattern or format a matching value can be built from.
  • CanonicalSchema::satisfiability answers No where a format takes no string of the length the schema asks for.

Fixed

  • CanonicalSchema::negate taking apart a union that reads a definition through its own if, so a schema and its negation shared a value.
  • CanonicalSchema::subtract dropping a Draft 4 array member an element demand partly takes.
  • CanonicalSchema::covers answering Yes where a Draft 4 element demand refuses a member.
  • A string schema whose maxLength is 0 keeping a pattern, format, or content facet unread, so the same constraints written in one object and written as an allOf reached different canonical forms.

Performance

  • not over a wide object schema costs its branch count instead of its square.
  • not over an object schema is linear in its property count, not quadratic.
  • not over an object schema with additionalProperties: false no longer costs cubic time in its property count.

... (truncated)

Commits
  • b7fd606 chore(rust): Release 0.51.0
  • b225a20 fix: Stack overflow compiling unevaluatedProperties or unevaluatedItems b...
  • df15d19 build(deps): bump crates/jsonschema/tests/suite
  • df8b81c fix: Misc format fixes
  • 38056c7 feat: ValidationOptions::with_vocabulary and the vocabularies attribute o...
  • 31d52b2 fix: The uniqueItems length ceiling not reading an items or contains sc...
  • 5993cf1 chore(ruby): Release 0.50.1
  • e04ecc6 build(ruby): Exclude arm-linux-musl
  • 1fc21b9 chore(python): Release 0.50.1
  • 60a563d chore(rust): Release 0.50.1
  • Additional commits viewable in compare view

Updates yaml_serde from 0.10.6 to 0.10.7

Commits

Updates vstd from 0.0.0-2026-08-09-0044 to 0.0.0-2026-08-23-0033

Commits

Updates uuid from 1.24.1 to 1.25.0

Release notes

Sourced from uuid's releases.

1.25.0

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@v1.24.1...1.25.0

Commits
  • 302e0bf Merge pull request #903 from uuid-rs/cargo/1.25.0
  • b7ccde8 prepare for 1.25.0 release
  • c62dffb Merge pull request #902 from ChrisJr404/serde-bytes-module
  • 8c198b2 Add a serde::bytes module that encodes as a byte string
  • See full diff in compare view

Updates jsonschema from 0.49.9 to 0.51.0

Release notes

Sourced from jsonschema's releases.

[Python] Release 0.51.0

Added

  • vocabularies option, declaring support for a vocabulary this library does not implement.

Fixed

  • The uniqueItems length ceiling not reading an items or contains schema written as a $ref.
  • The Draft 2020-12 Format-Assertion vocabulary read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • An unrecognized format accepted under a meta-schema requiring the Format-Assertion vocabulary (it should be rejected).
  • A meta-schema requiring a vocabulary this library does not implement accepted (it should be rejected).
  • The Draft 2019-09 Format vocabulary declared true read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • The bundled https://json-schema.org/draft/2020-12/meta/format-assertion meta-schema not declaring its vocabulary, so a schema written against it annotated format instead of asserting it.
  • A meta-schema without $id keeping its $vocabulary unread, so a schema written against it got every Draft 2020-12 vocabulary.
  • A schema naming a bundled vocabulary meta-schema as its $schema rejected as an unknown meta-schema (it should build).
  • The regex format reading the Rust regex dialect (it should read the ECMA-262 dialect in Unicode mode).
  • The uri-template format rejecting an apostrophe in a literal (it should accept it, per RFC 6570 errata 6937).
  • The duration format accepting weeks combined with a time part, such as P1WT1H (it should reject it).
  • Stack overflow compiling unevaluatedProperties or unevaluatedItems beside a $ref that cycles back to the node, written as #, through its $id, or through a chain of definitions.

Performance

  • Building unevaluatedProperties or unevaluatedItems over a deep allOf or $ref chain costs its depth instead of its square.

[Ruby] Release 0.51.0

Added

  • vocabularies option, declaring support for a vocabulary this library does not implement.

Fixed

  • The uniqueItems length ceiling not reading an items or contains schema written as a $ref.
  • The Draft 2020-12 Format-Assertion vocabulary read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • An unrecognized format accepted under a meta-schema requiring the Format-Assertion vocabulary (it should be rejected).
  • A meta-schema requiring a vocabulary this library does not implement accepted (it should be rejected).
  • The Draft 2019-09 Format vocabulary declared true read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • The bundled https://json-schema.org/draft/2020-12/meta/format-assertion meta-schema not declaring its vocabulary, so a schema written against it annotated format instead of asserting it.
  • A meta-schema without $id keeping its $vocabulary unread, so a schema written against it got every Draft 2020-12 vocabulary.
  • A schema naming a bundled vocabulary meta-schema as its $schema rejected as an unknown meta-schema (it should build).
  • The regex format reading the Rust regex dialect (it should read the ECMA-262 dialect in Unicode mode).
  • The uri-template format rejecting an apostrophe in a literal (it should accept it, per RFC 6570 errata 6937).
  • The duration format accepting weeks combined with a time part, such as P1WT1H (it should reject it).
  • Stack overflow compiling unevaluatedProperties or unevaluatedItems beside a $ref that cycles back to the node, written as #, through its $id, or through a chain of definitions.

Performance

  • Building unevaluatedProperties or unevaluatedItems over a deep allOf or $ref chain costs its depth instead of its square.

[Rust] Release 0.51.0

Added

... (truncated)

Changelog

Sourced from jsonschema's changelog.

[0.51.0] - 2026-08-23

Added

  • ValidationOptions::with_vocabulary and the vocabularies attribute on jsonschema::validator, declaring support for a vocabulary this crate does not implement.
  • The --vocabulary flag of jsonschema validate.

Changed

  • Vocabulary gained the FormatAssertion variant, which its Draft 2020-12 URI parses to instead of Vocabulary::Custom, and is marked non_exhaustive.

Fixed

  • The uniqueItems length ceiling not reading an items or contains schema written as a $ref.
  • The Draft 2020-12 Format-Assertion vocabulary read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • An unrecognized format accepted under a meta-schema requiring the Format-Assertion vocabulary (it should be rejected).
  • A meta-schema requiring a vocabulary this crate does not implement accepted (it should be rejected).
  • The Draft 2019-09 Format vocabulary declared true read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • The bundled https://json-schema.org/draft/2020-12/meta/format-assertion meta-schema not declaring its vocabulary, so a schema written against it annotated format instead of asserting it.
  • A meta-schema without $id keeping its $vocabulary unread, so a schema written against it got every Draft 2020-12 vocabulary.
  • A schema naming a bundled vocabulary meta-schema as its $schema rejected as an unknown meta-schema (it should build).
  • The regex format reading the Rust regex dialect (it should read the ECMA-262 dialect in Unicode mode).
  • The uri-template format rejecting an apostrophe in a literal (it should accept it, per RFC 6570 errata 6937).
  • The duration format accepting weeks combined with a time part, such as P1WT1H (it should reject it).
  • Stack overflow compiling unevaluatedProperties or unevaluatedItems beside a $ref that cycles back to the node, written as #, through its $id, or through a chain of definitions.

Performance

  • Building unevaluatedProperties or unevaluatedItems over a deep allOf or $ref chain costs its depth instead of its square.

[0.50.1] - 2026-08-22

Changed

  • CanonicalSchema::satisfiability answers Yes for a string whose pattern or format a matching value can be built from.
  • CanonicalSchema::satisfiability answers No where a format takes no string of the length the schema asks for.

Fixed

  • CanonicalSchema::negate taking apart a union that reads a definition through its own if, so a schema and its negation shared a value.
  • CanonicalSchema::subtract dropping a Draft 4 array member an element demand partly takes.
  • CanonicalSchema::covers answering Yes where a Draft 4 element demand refuses a member.
  • A string schema whose maxLength is 0 keeping a pattern, format, or content facet unread, so the same constraints written in one object and written as an allOf reached different canonical forms.

Performance

  • not over a wide object schema costs its branch count instead of its square.
  • not over an object schema is linear in its property count, not quadratic.
  • not over an object schema with additionalProperties: false no longer costs cubic time in its property count.

... (truncated)

Commits
  • b7fd606 chore(rust): Release 0.51.0
  • b225a20 fix: Stack overflow compiling unevaluatedProperties or unevaluatedItems b...
  • df15d19 build(deps): bump crates/jsonschema/tests/suite
  • df8b81c fix: Misc format fixes
  • 38056c7 feat: ValidationOptions::with_vocabulary and the vocabularies attribute o...
  • 31d52b2 fix: The uniqueItems length ceiling not reading an items or contains sc...
  • 5993cf1 chore(ruby): Release 0.50.1
  • e04ecc6 build(ruby): Exclude arm-linux-musl
  • 1fc21b9 chore(python): Release 0.50.1
  • 60a563d chore(rust): Release 0.50.1
  • Additional commits viewable in compare view

Updates yaml_serde from 0.10.6 to 0.10.7

Commits

Updates vstd from 0.0.0-2026-08-09-0044 to 0.0.0-2026-08-23-0033

Commits

Updates uuid from 1.24.1 to 1.25.0

Release notes

Sourced from uuid's releases.

1.25.0

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@v1.24.1...1.25.0

Commits
  • 302e0bf Merge pull request #903 from uuid-rs/cargo/1.25.0
  • b7ccde8 prepare for 1.25.0 release
  • c62dffb Merge pull request #902 from ChrisJr404/serde-bytes-module
  • 8c198b2 Add a serde::bytes module that encodes as a byte string
  • See full diff in compare view

Updates jsonschema from 0.49.9 to 0.51.0

Release notes

Sourced from jsonschema's releases.

[Python] Release 0.51.0

Added

  • vocabularies option, declaring support for a vocabulary this library does not implement.

Fixed

  • The uniqueItems length ceiling not reading an items or contains schema written as a $ref.
  • The Draft 2020-12 Format-Assertion vocabulary read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • An unrecognized format accepted under a meta-schema requiring the Format-Assertion vocabulary (it should be rejected).
  • A meta-schema requiring a vocabulary this library does not implement accepted (it should be rejected).
  • The Draft 2019-09 Format vocabulary declared true read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • The bundled https://json-schema.org/draft/2020-12/meta/format-assertion meta-schema not declaring its vocabulary, so a schema written against it annotated format instead of asserting it.
  • A meta-schema without $id keeping its $vocabulary unread, so a schema written against it got every Draft 2020-12 vocabulary.
  • A schema naming a bundled vocabulary meta-schema as its $schema rejected as an unknown meta-schema (it should build).
  • The regex format reading the Rust regex dialect (it should read the ECMA-262 dialect in Unicode mode).
  • The uri-template format rejecting an apostrophe in a literal (it should accept it, per RFC 6570 errata 6937).
  • The duration format accepting weeks combined with a time part, such as P1WT1H (it should reject it).
  • Stack overflow compiling unevaluatedProperties or unevaluatedItems beside a $ref that cycles back to the node, written as #, through its $id, or through a chain of definitions.

Performance

  • Building unevaluatedProperties or unevaluatedItems over a deep allOf or $ref chain costs its depth instead of its square.

[Ruby] Release 0.51.0

Added

  • vocabularies option, declaring support for a vocabulary this library does not implement.

Fixed

  • The uniqueItems length ceiling not reading an items or contains schema written as a $ref.
  • The Draft 2020-12 Format-Assertion vocabulary read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • An unrecognized format accepted under a meta-schema requiring the Format-Assertion vocabulary (it should be rejected).
  • A meta-schema requiring a vocabulary this library does not implement accepted (it should be rejected).
  • The Draft 2019-09 Format vocabulary declared true read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • The bundled https://json-schema.org/draft/2020-12/meta/format-assertion meta-schema not declaring its vocabulary, so a schema written against it annotated format instead of asserting it.
  • A meta-schema without $id keeping its $vocabulary unread, so a schema written against it got every Draft 2020-12 vocabulary.
  • A schema naming a bundled vocabulary meta-schema as its $schema rejected as an unknown meta-schema (it should build).
  • The regex format reading the Rust regex dialect (it should read the ECMA-262 dialect in Unicode mode).
  • The uri-template format rejecting an apostrophe in a literal (it should accept it, per RFC 6570 errata 6937).
  • The duration format accepting weeks combined with a time part, such as P1WT1H (it should reject it).
  • Stack overflow compiling unevaluatedProperties or unevaluatedItems beside a $ref that cycles back to the node, written as #, through its $id, or through a chain of definitions.

Performance

  • Building unevaluatedProperties or unevaluatedItems over a deep allOf or $ref chain costs its depth instead of its square.

[Rust] Release 0.51.0

Added

... (truncated)

Changelog

Sourced from jsonschema's changelog.

[0.51.0] - 2026-08-23

Added

  • ValidationOptions::with_vocabulary and the vocabularies attribute on jsonschema::validator, declaring support for a vocabulary this crate does not implement.
  • The --vocabulary flag of jsonschema validate.

Changed

  • Vocabulary gained the FormatAssertion variant, which its Draft 2020-12 URI parses to instead of Vocabulary::Custom, and is marked non_exhaustive.

Fixed

  • The uniqueItems length ceiling not reading an items or contains schema written as a $ref.
  • The Draft 2020-12 Format-Assertion vocabulary read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • An unrecognized format accepted under a meta-schema requiring the Format-Assertion vocabulary (it should be rejected).
  • A meta-schema requiring a vocabulary this crate does not implement accepted (it should be rejected).
  • The Draft 2019-09 Format vocabulary declared true read as an annotation, so a meta-schema requiring it accepted values its format rejects.
  • The bundled https://json-schema.org/draft/2020-12/meta/format-assertion meta-schema not declaring its vocabulary, so a schema written against it annotated format instead of asserting it.
  • A meta-schema without $id keeping its $vocabulary unread, so a schema written against it got every Draft 2020-12 vocabulary.
  • A schema naming a bundled vocabulary meta-schema as its $schema rejected as an unknown meta-schema (it should build).
  • The regex format reading the Rust regex dialect (it should read the ECMA-262 dialect in Unicode mode).
  • The uri-template format rejecting an apostrophe in a literal (it should accept it, per RFC 6570 errata 6937).
  • The duration format accepting weeks combined with a time part, such as P1WT1H (it should reject it).
  • Stack overflow compiling unevaluatedProperties or unevaluatedItems beside a $ref that cycles back to the node, written as #, through its $id, or through a chain of definitions.

Performance

  • Building unevaluatedProperties or unevaluatedItems over a deep allOf or $ref chain costs its depth instead of its square.

[0.50.1] - 2026-08-22

Changed

  • CanonicalSchema::satisfiability answers Yes for a string whose pattern or format a matching value can be built from.
  • CanonicalSchema::satisfiability answers No where a format takes no string of the length the schema asks for.

Fixed

  • CanonicalSchema::negate taking apart a union that reads a definition through its own if, so a schema and its negation shared a value.
  • CanonicalSchema::subtract dropping a Draft 4 array member an element demand partly takes.
  • CanonicalSchema::covers answering Yes where a Draft 4 element demand refuses a member.
  • A string schema whose maxLength is 0 keeping a pattern, format, or content facet unread, so the same constraints written in one object and written as an allOf reached different canonical forms.

Performance

  • not over a wide object schema costs its branch count instead of its square.
  • not over an object schema is linear in its property count, not quadratic.
  • not over an object schema with additionalProperties: false no longer costs cubic time in its property count.

... (truncated)

Commits
  • b7fd606 chore(rust): Release 0.51.0
  • b225a20 fix: Stack overflow compiling unevaluatedProperties or unevaluatedItems b...
  • df15d19 build(deps): bump crates/jsonschema/tests/suite
  • df8b81c fix: Misc format fixes
  • 38056c7 feat: ValidationOptions::with_vocabulary and the vocabularies attribute o...
  • 31d52b2 fix: The uniqueItems length ceiling not reading an items or contains sc...
  • 5993cf1 chore(ruby): Release 0.50.1
  • e04ecc6 build(ruby): Exclude arm-linux-musl
  • 1fc21b9 chore(python): Release 0.50.1
  • 60a563d chore(rust): Release 0.50.1
  • Additional commits viewable in compare view

Updates yaml_serde from 0.10.6 to 0.10.7

Commits

Updates vstd from 0.0.0-2026-08-09-0044 to 0.0.0-2026-08-23-0033

Commits

Updates ordered-float from 5.3.0 to 5.5.0

Release notes

Sourced from ordered-float's releases.

v5.5.0

  • Minimum supported Rust version increased from 1.63 to 1.90.
  • feat: derive Facet if facet feature is active by @​Erik1000 in #179

Full Changelog: reem/rust-ordered-float@v5.4.0...v5.5.0

v5.4.0

What's Changed

New Contributors

Full Changelog: reem/rust-ordered-float@v5.3.0...v5.4.0

Commits

Updates uuid from 1.24.1 to 1.25.0

Release notes

Sourced from uuid's releases.

1.25.0

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@v1.24.1...1.25.0

Commits
  • 302e0bf Merge pull request #903 from uuid-rs/cargo/1.25.0
  • b7ccde8 prepare for 1.25.0 release
  • c62dffb Merge pull request #902 from ChrisJr404/serde-bytes-module

@dependabot
build(deps): bump the rust-dependencies group across 5 directories wi…
2268faf 
…th 5 updates

Bumps the rust-dependencies group with 4 updates in the / directory: [uuid](https://github.com/uuid-rs/uuid), [jsonschema](https://github.com/Stranger6667/jsonschema), [yaml_serde](https://github.com/yaml/yaml-serde) and [vstd](https://github.com/verus-lang/verus).
Bumps the rust-dependencies group with 4 updates in the /bindings/ffi directory: [uuid](https://github.com/uuid-rs/uuid), [jsonschema](https://github.com/Stranger6667/jsonschema), [yaml_serde](https://github.com/yaml/yaml-serde) and [vstd](https://github.com/verus-lang/verus).
Bumps the rust-dependencies group with 4 updates in the /bindings/java directory: [uuid](https://github.com/uuid-rs/uuid), [jsonschema](https://github.com/Stranger6667/jsonschema), [yaml_serde](https://github.com/yaml/yaml-serde) and [vstd](https://github.com/verus-lang/verus).
Bumps the rust-dependencies group with 5 updates in the /bindings/python directory:

| Package | From | To |
| --- | --- | --- |
| [uuid](https://github.com/uuid-rs/uuid) | `1.24.1` | `1.25.0` |
| [jsonschema](https://github.com/Stranger6667/jsonschema) | `0.49.9` | `0.51.0` |
| [yaml_serde](https://github.com/yaml/yaml-serde) | `0.10.6` | `0.10.7` |
| [vstd](https://github.com/verus-lang/verus) | `0.0.0-2026-08-09-0044` | `0.0.0-2026-08-23-0033` |
| [ordered-float](https://github.com/reem/rust-ordered-float) | `5.3.0` | `5.5.0` |

Bumps the rust-dependencies group with 4 updates in the /bindings/wasm directory: [uuid](https://github.com/uuid-rs/uuid), [jsonschema](https://github.com/Stranger6667/jsonschema), [yaml_serde](https://github.com/yaml/yaml-serde) and [vstd](https://github.com/verus-lang/verus).


Updates `uuid` from 1.24.1 to 1.25.0
- [Release notes](https://github.com/uuid-rs/uuid/releases)
- [Commits](uuid-rs/uuid@v1.24.1...1.25.0)

Updates `jsonschema` from 0.49.9 to 0.51.0
- [Release notes](https://github.com/Stranger6667/jsonschema/releases)
- [Changelog](https://github.com/Stranger6667/jsonschema/blob/master/CHANGELOG.md)
- [Commits](Stranger6667/jsonschema@cli-v0.49.9...cli-v0.51.0)

Updates `yaml_serde` from 0.10.6 to 0.10.7
- [Commits](yaml/yaml-serde@0.10.6...0.10.7)

Updates `vstd` from 0.0.0-2026-08-09-0044 to 0.0.0-2026-08-23-0033
- [Release notes](https://github.com/verus-lang/verus/releases)
- [Commits](https://github.com/verus-lang/verus/commits)

Updates `uuid` from 1.24.1 to 1.25.0
- [Release notes](https://github.com/uuid-rs/uuid/releases)
- [Commits](uuid-rs/uuid@v1.24.1...1.25.0)

Updates `jsonschema` from 0.49.9 to 0.51.0
- [Release notes](https://github.com/Stranger6667/jsonschema/releases)
- [Changelog](https://github.com/Stranger6667/jsonschema/blob/master/CHANGELOG.md)
- [Commits](Stranger6667/jsonschema@cli-v0.49.9...cli-v0.51.0)

Updates `yaml_serde` from 0.10.6 to 0.10.7
- [Commits](yaml/yaml-serde@0.10.6...0.10.7)

Updates `vstd` from 0.0.0-2026-08-09-0044 to 0.0.0-2026-08-23-0033
- [Release notes](https://github.com/verus-lang/verus/releases)
- [Commits](https://github.com/verus-lang/verus/commits)

Updates `uuid` from 1.24.1 to 1.25.0
- [Release notes](https://github.com/uuid-rs/uuid/releases)
- [Commits](uuid-rs/uuid@v1.24.1...1.25.0)

Updates `jsonschema` from 0.49.9 to 0.51.0
- [Release notes](https://github.com/Stranger6667/jsonschema/releases)
- [Changelog](https://github.com/Stranger6667/jsonschema/blob/master/CHANGELOG.md)
- [Commits](Stranger6667/jsonschema@cli-v0.49.9...cli-v0.51.0)

Updates `yaml_serde` from 0.10.6 to 0.10.7
- [Commits](yaml/yaml-serde@0.10.6...0.10.7)

Updates `vstd` from 0.0.0-2026-08-09-0044 to 0.0.0-2026-08-23-0033
- [Release notes](https://github.com/verus-lang/verus/releases)
- [Commits](https://github.com/verus-lang/verus/commits)

Updates `uuid` from 1.24.1 to 1.25.0
- [Release notes](https://github.com/uuid-rs/uuid/releases)
- [Commits](uuid-rs/uuid@v1.24.1...1.25.0)

Updates `jsonschema` from 0.49.9 to 0.51.0
- [Release notes](https://github.com/Stranger6667/jsonschema/releases)
- [Changelog](https://github.com/Stranger6667/jsonschema/blob/master/CHANGELOG.md)
- [Commits](Stranger6667/jsonschema@cli-v0.49.9...cli-v0.51.0)

Updates `yaml_serde` from 0.10.6 to 0.10.7
- [Commits](yaml/yaml-serde@0.10.6...0.10.7)

Updates `vstd` from 0.0.0-2026-08-09-0044 to 0.0.0-2026-08-23-0033
- [Release notes](https://github.com/verus-lang/verus/releases)
- [Commits](https://github.com/verus-lang/verus/commits)

Updates `ordered-float` from 5.3.0 to 5.5.0
- [Release notes](https://github.com/reem/rust-ordered-float/releases)
- [Commits](reem/rust-ordered-float@v5.3.0...v5.5.0)

Updates `uuid` from 1.24.1 to 1.25.0
- [Release notes](https://github.com/uuid-rs/uuid/releases)
- [Commits](uuid-rs/uuid@v1.24.1...1.25.0)

Updates `jsonschema` from 0.49.9 to 0.51.0
- [Release notes](https://github.com/Stranger6667/jsonschema/releases)
- [Changelog](https://github.com/Stranger6667/jsonschema/blob/master/CHANGELOG.md)
- [Commits](Stranger6667/jsonschema@cli-v0.49.9...cli-v0.51.0)

Updates `yaml_serde` from 0.10.6 to 0.10.7
- [Commits](yaml/yaml-serde@0.10.6...0.10.7)

Updates `vstd` from 0.0.0-2026-08-09-0044 to 0.0.0-2026-08-23-0033
- [Release notes](https://github.com/verus-lang/verus/releases)
- [Commits](https://github.com/verus-lang/verus/commits)

---
updated-dependencies:
- dependency-name: uuid
  dependency-version: 1.25.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: rust-dependencies
- dependency-name: jsonschema
  dependency-version: 0.51.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: rust-dependencies
- dependency-name: yaml_serde
  dependency-version: 0.10.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust-dependencies
- dependency-name: vstd
  dependency-version: 0.0.0-2026-08-23-0033
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust-dependencies
- dependency-name: uuid
  dependency-version: 1.25.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: rust-dependencies
- dependency-name: jsonschema
  dependency-version: 0.51.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: rust-dependencies
- dependency-name: yaml_serde
  dependency-version: 0.10.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust-dependencies
- dependency-name: vstd
  dependency-version: 0.0.0-2026-08-23-0033
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust-dependencies
- dependency-name: uuid
  dependency-version: 1.25.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: rust-dependencies
- dependency-name: jsonschema
  dependency-version: 0.51.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: rust-dependencies
- dependency-name: yaml_serde
  dependency-version: 0.10.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust-dependencies
- dependency-name: vstd
  dependency-version: 0.0.0-2026-08-23-0033
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust-dependencies
- dependency-name: uuid
  dependency-version: 1.25.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: rust-dependencies
- dependency-name: jsonschema
  dependency-version: 0.51.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: rust-dependencies
- dependency-name: yaml_serde
  dependency-version: 0.10.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust-dependencies
- dependency-name: vstd
  dependency-version: 0.0.0-2026-08-23-0033
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust-dependencies
- dependency-name: ordered-float
  dependency-version: 5.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: rust-dependencies
- dependency-name: uuid
  dependency-version: 1.25.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: rust-dependencies
- dependency-name: jsonschema
  dependency-version: 0.51.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: rust-dependencies
- dependency-name: yaml_serde
  dependency-version: 0.10.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust-dependencies
- dependency-name: vstd
  dependency-version: 0.0.0-2026-08-23-0033
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update Rust code labels Aug 27, 2026
@anakrish
Pin vstd to Verus release version
c6eca8d 
Co-authored-by: anakrish <35780660+anakrish@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@anakrish Anand Krishnamoorthi (anakrish) anakrish approved these changes

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update Rust code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@anakrish